2 Messages

2.1 Applicable Messages

The following table is a full list of all ODF messages and describes the list of messages used in Cycling Mountain Bike .

The column “Message type“ indicates the DocumentType that identifies a message
The column “Message name“ is the message name identified by the message type
The column “Message extended“ indicates whether a particular message has extended definition in regards to those that are general for all sports. If one particular message is not extended, then it should follow the general definition rules.

Message Type	Message Name	Message extended
DT_SCHEDULE / DT_SCHEDULE_UPDATE	Competition schedule / Competition schedule update
DT_PARTIC / DT_PARTIC_UPDATE	List of participants by discipline / List of participants by discipline update	X
DT_MEDALS	Medal standings
DT_MEDALLISTS_DAY	Medallists of the day
DT_GLOBAL_GM	Global good morning
DT_GLOBAL_GN	Global good night
DT_RESULT	Event Unit Start List and Results	X
DT_PLAY_BY_PLAY	Play by Play	X
DT_IMAGE	Image	X
DT_PRESSPHOTOFINISH_LK	Press Photofinish
DT_RANKING	Event Final Ranking
DT_COMMUNICATION	Official Communication
DT_CONFIG	Configuration	X
DT_WEATHER	Event Unit Weather conditions	X
DT_MEDALLISTS	Event's Medallists
DT_MEDALLISTS_DISCIPLINE	Medallists by discipline
DT_LOCAL_OFF	Discipline/venue stop transmission
DT_LOCAL_ON	Discipline/venue start transmission
DT_KA	Keep Alive

2.2 Messages

2.2.1 List of participants by discipline / List of participants by discipline update

2.2.1.1 Description

A participant is considered to be any individual (type athlete, participating or not in the current games) or any official in one or several disciplines or a competitor being part of a team (team member).

Although the participant may participate in more than one event or more than one discipline, this message just contains the information for the discipline of the message, listing the information of all the events for that discipline.

This message includes historical athletes that do not participate in the current competition. Historical athletes will not be registered to any event.

It is important to note that all the sport messages that make references to athletes (start list, event unit results, etc.) will always match the athlete ID with the athlete ID in this message. The historical athletes will be used to match historical athlete information as it appears in the records message when sending the previous record information and this previous record was an historical record not being broken in the current competition.

List of participants by discipline (DT_PARTIC) is a bulk message, provided for each discipline. It is a complete participant information message for one particular discipline. The arrival of this message resets all the previous participants' information for one particular discipline. This message can include a list of current athletes, officials, coaches, guides, technical officials, Reserves and historical athletes.

List of participants by discipline update (DT_PARTIC_UPDATE) is an update message. It is not a complete list of participants' information by discipline message, only the participant data being modified, i.e. if some data of one participant changes, the element Participant for it with all its children and attributes must be sent.

The key of the information updated consists of the following attribute: Participant @Code. Therefore, any new or updated Participant Discipline-Event will be identified by all these attributes.

2.2.1.2 Header Values

The following table describes the message header attributes.

Attribute	Value	Comment
CompetitionCode	CC @Competition	Unique ID for competition
DocumentCode	DD0000000	DD is defined according to CC @Discipline
DocumentType	DT_PARTIC / DT_PARTIC_UPDATE	List of participants by discipline message
Version	1..V	Version number associated to the message's content. Ascendant number
FeedFlag	"P"-Production "T"-Test	Test message or production message.
Date	Date	Date when the message is generated, expressed in the local time zone where the message was produced.
Time	Time	Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.
LogicalDate	Date	Logical Date of events. This is the same as the physical day except when the unit or message transmission extends after midnight. If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the message will all be dated Aug 2). The end of the logical day is defined by default at 03:00 a.m. For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the day of the correction. Logical Date is expressed in the local time zone where the message was produced.
Source	SC @Source	Code indicating the system which generated the message.
Serial	Numeric	Sequence number (positive integer) for ODF messages. Serial starts with 1 each day for each Source.

2.2.1.3 Trigger and Frequency

The DT_PARTIC message is sent as a bulk message approximately one month before the Games. It is sent several times up to the date of transfer of control to OVR after which only DT_PARTIC_UPDATE messages are sent.

The DT_PARTIC_UPDATE message is triggered when there is a modification in the data for any individual after the transfer of control to OVR.

2.2.1.4 Message Structure

The following table defines the structure of the message.

Level 1	Level 2	Level 3	Level 4	Level 5	Level 6
Competition (1,1)
	Code
	Participant (1,N)
		Code
		Parent
		Status
		GivenName
		FamilyName
		PrintName
		PrintInitialName
		TVName
		TVInitialName
		Gender
		Organisation
		BirthDate
		Height
		Weight
		PlaceofBirth
		CountryofBirth
		PlaceofResidence
		CountryofResidence
		Nationality
		MainFunctionId
		Current
		OlympicSolidarity
		ModificationIndicator
		Discipline (1,1)
			Code
			IFId
			DisciplineEntry (0,N)
				Code
				Type
				Pos
			RegisteredEvent (0,N)
				Gender
				Event
				Bib
				EventEntry (0,N)
					Code
					Type
					Pos
					Value
		OfficialFunction (0,N)
			FunctionId

2.2.1.5 Message Values

Element: Competition (1,1)

Attribute

M/O

Value

Description

Code

CC @Competition

Unique ID for competition

Code is deprecated and value is duplicated in the header.

Element: Participant (1,N)

Attribute	M/O	Value	Description
Code	M	S(20) with no leading zeroes	Participant's ID. It identifies an athlete or an official and the holding participant's valid information for one particular period of time. It is used to link other messages to the participant's information. Participant's information (example @Organisation) will not be the latest for the athlete/official, unless the @Code attribute is the same as the @Parent attribute. However, this information could be the one being valid in the particular moment of a start list, event unit results, etc. When the participant is an historical one, then this ID will start with "A" when it is an Athlete, "C" when Coach and "O" when Official.
Parent	M	S(20) with no leading zeroes	Participant's parent ID, which is used to link to the latest valid information for one participant. @Parent attribute should be linked to the latest participant's information, by retrieving that Athlete/Official whose @Code attribute is the same as @Parent. The participant containing @Code attribute being the same as the @Parent attribute will be the one with the latest information for the participant. The @Parent attribute will only be different from @Code in the case that critial personal information has changed from previous competitions. The typical examples are Organisation (for change of country) or Name (particularly for women changing their name at marriage). Further to be clear, @Parent and @Code can only be different if Current = "false".
Status	O	CC @ParticStatus	Participant's accreditation status this atribute is Mandatory in the case of @Current="true" and it is optional in the case that @Current="false". To delete a participant, a specific value of the Status attribute is used.
GivenName	O	S(25)	Given name in WNPA format (mixed case)
FamilyName	M	S(25)	Family name in WNPA format (mixed case)
PrintName	M	S(35)	Print name (family name in upper case + given name in mixed case)
PrintInitialName	M	S(18)	Print Initial name (for the given name it is sent just the initial, without dot)
TVName	M	S(35)	TV name
TVInitialName	M	S(18)	TV initial name
Gender	M	CC @PersonGender	Participant's gender
Organisation	M	CC @Organisation	Organisation ID
BirthDate	O	YYYY-MM-DD	Date of birth. This information may not be known at the very beginning, but it will be completed for all participants after successive updates
Height	O	S(3)	Height in centimetres. It will be included if this information is available. This information is not needed in the case of officials/referees. "-" may be used where the data is not available.
Weight	O	S(3)	Weight in kilograms. It will be included if this information is available. This information is not needed in the case of officials/referees. "-" may be used where the data is not available.
PlaceofBirth	O	S(75)	Place of Birth
CountryofBirth	O	CC @Country	Country ID of Birth
PlaceofResidence	O	S(75)	Place of Residence
CountryofResidence	O	CC @Country	Country ID of Residence
Nationality	O	CC @Country	Participant's nationality. Although this attribute is optional, in very exceptional situations it will not be known, and for this reason not ready to be sent.
MainFunctionId	O	CC @ResultsFunction	Main function In the Case of Current="true" this attribute is Mandatory.
Current	M	boolean	It defines if a participant is participating in the games (true) or is a Historical participant (false).
OlympicSolidarity	O	Y or N	Flag to indicating if the participant participates in the Olympic Scholarship program.
ModificationIndicator	M	S(1)	'N' or 'U' Attribute is mandatory in the DT_PARTIC_UPDATE message only N-New participant (in the case that this information comes as a late entry) U-Update participant If ModificationIndicator='N', then include new participant to the previous bulk-loaded list of participants If ModificationIndicator='U', then update the participant to the previous bulk-loaded list of participants To delete a participant, a specific value of the Status attribute is used.

Element: Participant /Discipline (1,1)

All participating athletes will be assigned at least one discipline, it could be more. Each accredited official will be assigned at least one discipline, but it could be more. If an athlete or official is assigned to more than one discipline, it will be included in the participant message of both disciplines.

Attribute	M/O	Value	Description
Code	M	CC @Discipline	It is the discipline code used to fill the OdfBody @DocumentCode attribute.
IFId	O	S(16)	UCI code (competitor's federation number for the discipline).

Element: Participant /Discipline /DisciplineEntry (0,N)

Send if there is specific discipline information.

Type

Code

Pos

Description

Element: Participant /Discipline /RegisteredEvent (0,N)

All accredited athletes will be assigned to one or more events. There is one exception: in some sports, substitutes may be accredited without any associated event. Historical athletes are not registered to any event.

Attribute	M/O	Value	Description
Gender	M	CC @DisciplineGender	Discipline Gender Code
Event	M	CC @Event	Event ID
Bib	O	S(2)	Bib number. Although this attribute is optional, it will be updated and informed as soon as this information is known. Example: 8, 10,..Send only in the Case of Current="true".

Element: Participant /Discipline /RegisteredEvent /EventEntry (0,N)

Send if there are specific athlete's event entries.

	Type	Code	Pos	Description
ENTRY		RANK_WLD	N/A	Element Expected: As soon as the venue results has this information (this information can be sent in both messages)
	Attribute	M/O	Value	Description
	Value	M	S(4)	Send the UCI ranking for the competitor.
ENTRY		UCIRIDERID	N/A	Element Expected: As soon as the venue results has this information (this information can be sent in both messages)
	Attribute	M/O	Value	Description
	Value	M	S(16)	Send the UCI unique rider ID.

Element: Participant /OfficialFunction (0,N)

Send if the official has optional functions. Do not send, otherwise.

Attribute	M/O	Value	Description
FunctionId	M	CC @ResultsFunction	Additional officials' function code

2.2.1.6 Message Sort

The message is sorted by Participant @Code

2.2.2 Event Unit Start List and Results

2.2.2.1 Description

The Event Unit Start List and Results is a message containing both the start list and results information of the competitors in one (individual or team) event unit.

The Event Unit Start List and Results is a mandatory message for all sports. The definition includes as much generic information as possible due to the fact that each discipline and event has its own format for the results information (example: score of a match, time in a race, distance in a throw...).

This is always a full message and all applicable elements and attributes are always sent.

2.2.2.2 Header Values

The following table describes the message header attributes.

Attribute	Value	Comment
CompetitionCode	CC @Competition	Unique ID for competition
DocumentCode	DDGEEEPUU	DD according to CC @Discipline G according to CC @DisciplineGender EEE according to CC @Event P according to CC @Phase UU according to CC @Unit The DocumentCode will be sent according to the ODF Common Codes document (header values sheet)
DocumentType	DT_RESULT	Event Unit Start List and Results message
DocumentSubtype	Not used in CM	Not used in CM
Version	1..V	Version number associated to the message's content. Ascendant number
ResultStatus	SC @ResultStatus	It indicates whether the result is official or unofficial (or intermediate etc). START_LIST OFFICIAL UNOFFICIAL INTERMEDIATE (used after the competition has started and is not finished but not currently live) LIVE (used during the competition when nothing else applies).
FeedFlag	"P"-Production "T"-Test	Test message or production message.
Date	Date	Date when the message is generated, expressed in the local time zone where the message was produced.
Time	Time	Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.
LogicalDate	Date	Logical Date of events. This is the same as the physical day except when the unit or message transmission extends after midnight. If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the message will all be dated Aug 2). The end of the logical day is defined by default at 03:00 a.m. For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the day of the correction. Logical Date is expressed in the local time zone where the message was produced.
Source	SC @Source	Code indicating the system which generated the message.
StartListMod	S(1)	Send Y if the start list has been changed with this message and the ResultStatus is not START_LIST. Do not send the attribute if it is not Y. Only send once for each start list change. In this case the full current message is sent with whatever is the current ResultStatus. The Start List is considered to be changed if any of the following changes: * Competitors or athletes are added, changed or removed including in <ExtendedInfos /Competitor> * Any change in <Officials> * Any change in StartOrder or StartSortOrder * Any changes in <Coaches> * Any changes in <EventUnitEntry> Changing descriptions is not considered a start list change.
Serial	Numeric	Sequence number (positive integer) for ODF messages. Serial starts with 1 each day for each Source.

2.2.2.3 Trigger and Frequency

This message is sent with ResultStatus 'START_LIST' as soon as the expected information is available and any changes to the information. Possible information is:

* As soon as the start list is available and any changes [inc. IRMs] (START_LIST)

This message is then sent with ResultStatus 'LIVE' as soon as the unit starts and continues to be triggered on all updates.

* When the competition starts and all changes/additions in data (LIVE)

This message is also sent when the event unit finishes and the results are still unofficial. Also, this message is expected when the results become official. The official/unofficial status is included in the ODF headers (ResultStatus attribute).

* When the last competitor finish (UNOFFICIAL)

* After the results for the race are approved (OFFICIAL)

Trigger also after any change.

2.2.2.4 Message Structure

The following table defines the structure of the message.

Level 1	Level 2	Level 3	Level 4	Level 5	Level 6	Level 7	Level 8
Competition (1,1)
	Code
	ExtendedInfos (0,1)
		UnitDateTime (0,1)
			StartDate
			EndDate
		ExtendedInfo (0,N)
			Type
			Code
			Pos
			Value
			Extension (0,N)
				Code
				Pos
				Value
		SportDescription (0,1)
			DisciplineName
			EventName
			Gender
			SubEventName
		VenueDescription (0,1)
			Venue
			VenueName
			Location
			LocationName
	Result (1,N)
		Rank
		RankEqual
		Result
		Unchecked
		IRM
		SortOrder
		StartOrder
		StartSortOrder
		ResultType
		Diff
		Competitor (1,1)
			Code
			Type
			Organisation
			Composition (0,1)
				Athlete (1,N)
					Code
					Order
					Bib
					Description (1,1)
						GivenName
						FamilyName
						Gender
						Organisation
						BirthDate
						IFId
					EventUnitEntry (0,N)
						Type
						Code
						Pos
						Value
					ExtendedResults (0,1)
						ExtendedResult (1,N)
							Type
							Code
							Pos
							Value
							ValueType
							Rank
							RankEqual
							SortOrder
							Diff
							Speed

2.2.2.5 Message Values

Element: Competition (1,1)

Attribute

M/O

Value

Description

Code

CC @Competition

Unique ID for competition

Code is deprecated and value is duplicated in the header.

Element: ExtendedInfos /UnitDateTime (0,1)

Scheduled start date and time. (where available update with actual start time)

Actual start -and/or end- dates and times.

Attribute	M/O	Value	Description
StartDate	O	DateTime	Actual start date and time. For multiday units, the start time is on the first day.
EndDate	O	DateTime	Actual end date-time

Element: ExtendedInfos /ExtendedInfo (0,N)

	Type	Code	Pos	Description
DISPLAY		LAST_COMP	Numeric 0	Pos Description: Sent INTERMEDIATE @Pos in ExtendedInfos for the last intermediate passed by the most recent athlete to pass any intermediate point. Element Expected: When available and only when the unit is LIVE
	Attribute	M/O	Value	Description
	Value	M	Numeric 0	Send the competitor ID of the last competitor to pass the intermediate point @Pos
UI		AFTER_N	N/A	Element Expected: When was available
	Attribute	M/O	Value	Description
	Value	M	String	Athletes passed point x riders have completed y distance (z Km)
UI		ENTRIES	N/A	Element Expected: When was available
	Attribute	M/O	Value	Description
	Value	M	Numeric	Send the number of entries
UI		FASTEST	Numeric #0	Pos Description: Send the lap's number in which the competitor had the best time. Element Expected: Send only at the end of the race
	Attribute	M/O	Value	Description
	Value	M	S(20) with no leading zeroes	To know the fastest competitor and in which lap happened Send the ID of the competitor with the fastest lap
UI		FINISHED	N/A	Element Expected: When was available
	Attribute	M/O	Value	Description
	Value	M	Numeric	Send number of riders who have finished the race.
UI		NOCS	N/A	Element Expected: When was available
	Attribute	M/O	Value	Description
	Value	M	Numeric	Send the number of NOCs
UI		y Where y=CC@IRM	N/A	Element Expected: When was available
	Attribute	M/O	Value	Description
	Value	M	Numeric	Send number of riders who have an IRM.
UI_LEADER		CURRENT	Numeric #0	Pos Description: Send the intermediate point where the current leader has most recently passed Element Expected: When it is available
	Attribute	M/O	Value	Description
	Value	M	S(20) with no leading zeroes	Send the Current Leader ID at the intermediate point
UI_LEADER		INTERMEDIATE	Numeric #0	Pos Description: The number that identifies the intermediate result point, from 1 to the total number (n) of intermediate result points. Where n is when finish the race. According to the @pos of the EC_RACE /INTERMEDIATE code at the DT_CONFIG message Element Expected: When it is available
	Attribute	M/O	Value	Description
	Value	O	h:mm:ss	Time up to that point of athlete who is leader at the intermediate point. Without leading zeros
	Sub Element: ExtendedInfos /ExtendedInfo /Extension Expected: When it is available
	Attribute	Value	Description
	Code	LAP_SPEED_AVG
	Pos	N/A	N/A
	Value	Numeric ##0.000	Average Speed of rider leader at last lap. km/h
	Sub Element: ExtendedInfos /ExtendedInfo /Extension Expected: When it is available
	Attribute	Value	Description
	Code	SPEED_AVG
	Pos	N/A	N/A
	Value	Numeric ##0.000	Average Speed, from the start, for athlete leader at each point.
UI_LEADER		SECTION	Numeric #0	Pos Description: The number that identifies the lap, from 1 to the total number (n) of laps. According to the @pos of the INTERMEDIATE code Element Expected: When it is available
	Attribute	M/O	Value	Description
	Value	O	h:mm:ss	Time for that lap. Do not send h if it is zero.
	Sub Element: ExtendedInfos /ExtendedInfo /Extension Expected: When it is available
	Attribute	Value	Description
	Code	SPEED_AVG
	Pos	N/A	N/A
	Value	Numeric ##0.000	Leader Average Speed in that section

Sample (Sample)

....

</ExtendedInfo>

....

</ExtendedInfo>

</ExtendedInfo>

....

</ExtendedInfo>

</ExtendedInfos>

....

Element: ExtendedInfos /SportDescription (0,1)

Sport Descriptions in Text.

Attribute	M/O	Value	Description
DisciplineName	M	S(40)	Discipline name (not code) from Common Codes
EventName	M	S(40)	Event name (not code) from Common Codes
Gender	M	CC @DisciplineGender	Gender code for the event unit
SubEventName	M	S(40)	EventUnit short name (not code) from Common Codes

Element: ExtendedInfos /VenueDescription (0,1)

Venue Names in Text.

Attribute	M/O	Value	Description
Venue	M	CC @VenueCode	Venue Code
VenueName	M	S(25)	Venue short name (not code) from Common Codes
Location	M	CC @Location	Location code
LocationName	M	S(30)	Location short name (not code) from Common Codes

Element: Result (1,N)

For each Event Unit Results message, there must be at least one competitor with a result element in the event unit.

Attribute	M/O	Value	Description
Rank	O	Text	Rank of the competitor in the corresponding event unit.
RankEqual	O	Y	Identifies if a rank has been equalled. Only send if applicable
Result	O	h:mm:ss	The result of the competitor in the event unit. Do not include h if it is zero.
Unchecked	O	S(1)	Send "Y" if time is a transponder time or similar and needs to be validated by reading photo. Do not send if not "Y".
IRM	O	SC @IRM	IRM for the particular event unit. Send just in the case @ResultType is IRM or RANK.
SortOrder	M	Numeric	Used to sort all the results of an event unit This attribute is a sequential number with the order of the results for the particular event unit Before the race start content is the same than StartSortOrder. After the first split data arrives, Results are sorted by split rank. For those athletes without rank (first split) then the sort is the same as before the race, but following athletes with split rank. At the end Results are sorted by Rank. The rank sort is, all those athletes at the forward most split are ranked 1 - x, adding those athletes that have not arrived to this split, which are sorted according position in previous split etc. back through each split (or start order). Resort as each new data item arrives. Athletes who are disqualified or are notified as "did not finish" during the race must be dropped to the bottom with no rank. DNF, DSQ and DNF will be grouped separately in the order defined by the international federation. Overlapped (LAP) riders must be dropped to the bottom also but above the DNF/DSQ/DNS riders.
StartOrder	M	Numeric	Line-up (Line number).
StartSortOrder	M	Numeric	Order in the Start_list. Used to sort all start list competitors in an event unit.
ResultType	O	SC @ResultType	Type of the @Result attribute.
Diff	O	String	Time behind at finish only (for leader is +0:00)

Element: Result /Competitor (1,1)

Competitor related to the result of one event unit.

Attribute	M/O	Value	Description
Code	M	S(20) with no leading zeroes or TBD or NOCOMP	Competitor's ID or TBD in case that the competitor is unknown at this time but will be available NOCOMP is sent when there is no competitor (and will not come later)
Type	M	A	A for athlete
Organisation	O	CC @Organisation	Competitor's organisation

Element: Result /Competitor /Composition /Athlete (1,N)

Attribute	M/O	Value	Description
Code	M	S(20) with no leading zeroes	Athlete's ID. Can belong to a team member or an individual athlete.
Order	M	Numeric	1 if Competitor @Type="A".
Bib	O	S(2)	Bib number

Element: Result /Competitor /Composition /Athlete /Description (1,1)

Athletes extended information.

Attribute	M/O	Value	Description
GivenName	O	S(25)	Given name in WNPA format (mixed case)
FamilyName	M	S(25)	Family name in WNPA format (mixed case)
Gender	M	CC @PersonGender	Gender of the athlete
Organisation	M	CC @Organisation	Athletes' organisation
BirthDate	O	Date	Birth date (example: YYYY-MM-DD). Must include if the data is available
IFId	O	S(16)	International Federation ID

Element: Result /Competitor /Composition /Athlete /EventUnitEntry (0,N)

Individual athletes entry information.

	Type	Code	Pos	Description
EUE		RANK	N/A	Element Expected: Always when available
	Attribute	M/O	Value	Description
	Value	M	Numeric ####	UCI Ranking

Sample (Sample)

....

....

Element: Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult (1,N)

Team member or individual athlete's extended result.

	Type	Code	Pos	Description
ER		CURRENT	N/A	Element Expected: Always when LIVE
	Attribute	M/O	Value	Description
	Value	M	Numeric #0	Intermediate point was the athlete has most recently passed If the competitor has an IRM: 1. In case the DNS or the athlete has an IRM before he crosses the first intermediate point: send 0. 2. In other cases, send the Intermediate point that he has crossed most recently. (Starting by 1. Start point (0) not considered if athlete don't gets an IRM)
ER		IRM_LAP	N/A	Element Expected: Only If the @IRM=LAP or @IRM=DNF
	Attribute	M/O	Value	Description
	Value	M	Numeric #0	If the @IRM=LAP Send the laps remaining for finish the race. If the @IRM=DNF Send the lap when the competitor left the race. Example: If the rider abandoned in lap 0 @IRM="DNF" IRM@Value=0 If the rider abandoned in lap 3 @IRM="DNF" IRM@Value=3 If the rider lapped with 4 laps remaining @IRM="LAP" IRM@Value=4
ER		PHOTO	N/A	Element Expected: At the end of the race. Only send for competitor who needs that.
	Attribute	M/O	Value	Description
	Value	M	S(1)	To know if the competitor's final result was decided by photo. Send P for Pending Status. Otherwise do not send. If PHOTO is sent as pending then those pending competitors will not have rank but will still be sorted in the correct place (as well as is known). For example: Rank = 1,2,,,5,6,7... and SortOrder = 1,2,3,4,5,6,7
PROGRESS		INTERMEDIATE	Numeric #0	Pos Description: Intermediate point where the competition has taken place (1,2..) (Including the Finish point) Element Expected: When it is available
	Attribute	M/O	Value	Description
	Value	O	h:mm:ss	Cumulative time after the intermediate point (@pos) Do not send h if it is zero.
	ValueType	O	SC @ResultType	ValueType should be used to describe the type of data @Value
	Rank	O	Text	Send the cumulative rank of the competitor at the intermediate point. Do not send if no value.
	RankEqual	O	Y	Send 'Y' if rank is equalled, otherwise do not send.
	SortOrder	M	Numeric	Send the order of the competitor at the corresponding point Order based on whole list (with the ones who have not passed yet are ordered as well - after the ones who have finished, but before the IRMs. Sorted by the intermediate passed most recently and by order there (if none, then by start order)). Overlapped (LAP) riders must be dropped to the bottom but above the DNF/DSQ/DNS riders. For tied athletes, the rider with the lowest bib number is listed first. E.g.: If the leader (ATH1) is in the intermediate point 3 and the Athlete AT2 just to pass that point so the values for these athletes are AT1 @SortOrder 1 INTERMEDIATE 3 AT2 @SortOrder 2 INTERMEDIATE 3 Then If the Athlete AT2 is the first to pass the intermediate point 4, he will be the new leader in that point so the values for these athletes are: AT2 INTERMEDIATE 3 / SortOrder 2 INTERMEDIATE 4 / SortOrder 1 AT1 INTERMEDIATE 3 / SortOrder 1 INTERMEDIATE 4 / SortOrder 2
	Diff	O	Time	Send the time behind the leader at the corresponding point. (Format +h:mm:ss or +0:00 for the leader. Do not send H is zero
	Speed	O	Numeric ##0.000	Send the average speed of the competitor up to that point.
PROGRESS		SECTION	Numeric #0	Pos Description: Section between the intermediate points delimiting a Lap. The section 1 is the first SECTION (usually Start Loop). Use as in ExtendedInfos. Element Expected: When it is available
	Attribute	M/O	Value	Description
	Value	O	h:mm:ss	Time for that lap. Do not send h if it is zero.
	ValueType	O	SC @ResultType	ValueType should be used to describe the type of data @Value
	Rank	O	Text	Rank of the competitor in the section.
	RankEqual	O	Y	Send 'Y' if rank is equalled, otherwise do not send.
	SortOrder	M	Numeric	Index based on whole list (with the ones who have not completed the SECTION as well - after the ones who have finished, but before the IRMs. Sorted by the intermediate passed most recently and by order there (if none, then by start order)). Overlapped (LAP) riders must be dropped to the bottom but above the DNF/DSQ/DNS riders. For tied athletes, the rider with the lowest bib number is listed first.
	Diff	O	Time	Send the time behind the fastest in the corresponding SECTION. (Format +h:mm:ss or + 0:00 for the leader. Do not send H is zero)
	Speed	O	Numeric ##0.000	Send the average speed of the competitor in the SECTION.

Sample (Sample)

....

....

</ExtendedResult>

....

</ExtendedResult>

....

</ExtendedResult>

....

</Athlete>

</Composition>

</Competitor>

</Result>

....

2.2.2.6 Message Sort

Sort by Result @SortOrder

2.2.3 Play by Play

2.2.3.1 Description

The Play by Play is a message containing official raw data from the results provider.

The message contains a generic definition that can be used to provide results data of different nature as well as all of the actions in a unit.

2.2.3.2 Header Values

The following table describes the message header attributes.

Attribute	Value	Comment
CompetitionCode	CC @Competition	Unique ID for competition
DocumentCode	DDGEEEPUU	DD according to CC @Discipline G according to CC @DisciplineGender EEE according to CC @Event P according to CC @Phase UU according to CC @Unit
DocumentSubcode	Not used for CM.	Not used for CM.
DocumentType	DT_PLAY_BY_PLAY	Play by Play message
Version	1..V	Version number associated to the message's content. Ascendant number
ResultStatus	SC @ResultStatus	Status of the message. Possible values are: START_LIST (only used if there are actions before the start) LIVE (used during the competition when nothing else applies) INTERMEDIATE UNCONFIRMED UNOFFICIAL OFFICIAL (when results official)
FeedFlag	"P"-Production "T"-Test	Test message or production message.
Date	Date	Date when the message is generated, expressed in the local time zone where the message was produced.
Time	Time	Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.
LogicalDate	Date	Logical Date of events. This is the same as the physical day except when the unit or message transmission extends after midnight. If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the message will all be dated Aug 2). The end of the logical day is defined by default at 03:00 a.m. For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the day of the correction. Logical Date is expressed in the local time zone where the message was produced.
Source	SC @Source	Code indicating the system which generated the message.
Serial	Numeric	Sequence number (positive integer) for ODF messages. Serial starts with 1 each day for each Source.

2.2.3.3 Trigger and Frequency

Messages will be generated with this frequency and status

* After every race incident (LIVE)(UNOFFICIAL if any new incident after race and before results be official)

* After the race (unit) (OFFICIAL).

2.2.3.4 Message Structure

The following table defines the structure of the message.

Level 1	Level 2	Level 3	Level 4	Level 5	Level 6	Level 7	Level 8
Competition (1,1)
	Code
	ExtendedInfos (0,1)
		ExtendedInfo (0,N)
			Type
			Code
			Pos
			Value
		SportDescription (0,1)
			DisciplineName
			EventName
			SubEventName
			Gender
		VenueDescription (0,1)
			Venue
			VenueName
			Location
			LocationName
	UnitActions (0,1)
		UnitAction (1,N)
			Code
			Type
			Pos
			Result
			Competitor (0,N)
				Code
				Type
				Order
				Organisation
				Composition (0,1)
					Athlete (1,N)
						Code
						Order
						Bib
						Description (1,1)
							GivenName
							FamilyName
							Gender
							Organisation
							BirthDate
							IFId

2.2.3.5 Message Values

Element: Competition (1,1)

Attribute

M/O

Value

Description

Code

CC @Competition

Unique ID for competition

Code is deprecated and value is duplicated in the header.

Element: ExtendedInfos /ExtendedInfo (0,N)

	Type	Code	Pos	Description
EI		AFTER_DIST	N/A	Element Expected: When available
	Attribute	M/O	Value	Description
	Value	M	String	The race distance completed so far Example: Lap 4, 56km or just 56km

Element: ExtendedInfos /SportDescription (0,1)

Sport Descriptions in Text.

Attribute	M/O	Value	Description
DisciplineName	M	S(40)	Discipline name (not code) from Common Codes
EventName	M	S(40)	Event name (not code) from Common Codes
SubEventName	O	S(40)	EventUnit short name (not code) from Common Codes
Gender	M	CC @DisciplineGender	Gender code for the event unit

Element: ExtendedInfos /VenueDescription (0,1)

Venue Names in Text.

Attribute	M/O	Value	Description
Venue	M	CC @VenueCode	Venue Code
VenueName	M	S(25)	Venue short name (not code) from Common Codes
Location	M	CC @Location	Location code
LocationName	M	S(30)	Location short name (not code) from Common Codes

Element: UnitActions /UnitAction (1,N)

	Type	Code	Pos	Description
UAC		Text	Numeric #0	Code Description: When in race (km or lap etc.) Pos Description: Unique sequential number for all the incidents from 1 to n (from the first incident to the last one). Element Expected: For each action
	Attribute	M/O	Value	Description
	Result	O	Text	Incident Description

Element: UnitActions /UnitAction /Competitor (0,N)

Competitor participating in the UnitAction. Used when the UnitAction is related to a competitor.

Attribute	M/O	Value	Description
Code	M	S(20) with no leading zeroes	Competitor's ID
Type	M	A	A for athlete
Order	M	Numeric	Order in which the competitor should appear for the action, if there is more than one competitor
Organisation	M	CC @Organisation	Competitors' organisation

Element: UnitActions /UnitAction /Competitor /Composition /Athlete (1,N)

Attribute	M/O	Value	Description
Code	M	S(20) with no leading zeroes	Athlete's ID ( individual athlete or team member) related to the action
Order	M	Numeric	Order of the athletes. Used to order the athletes when there are more than one athlete related to the action.
Bib	O	S(2)	Bib number

Element: UnitActions /UnitAction /Competitor /Composition /Athlete /Description (1,1)

Athletes extended information

Attribute	M/O	Value	Description
GivenName	O	S(25)	Given name in WNPA format (mixed case)
FamilyName	M	S(25)	Family name in WNPA format (mixed case)
Gender	M	CC @PersonGender	Gender of the athlete
Organisation	M	CC @Organisation	Athletes' organisation
BirthDate	O	Date	Birth date (example: YYYY-MM-DD). Must include if the data is available
IFId	O	S(16)	International Federation ID

Sample (Sample)

....

</ExtendedInfos>

....

</Athlete>

</Composition>

</Competitor>

</Athlete>

</Composition>

</Competitor>

....

</UnitAction>

....

2.2.3.6 Message Sort

UnitActions /UnitAction @Code followed by @Pos will be used to sort actions (if actions are

requested).

2.2.4 Image

2.2.4.1 Description

The 'Image message' is a message containing an image or images file(s) in .jpg or .png format encapsulated in a XML message.

The type of image may vary from discipline to discipline and could be a photofinish image or some other type of image to support the results of the discipline.

The message allows for multiple images but it is assumed the images are related (could be different resolutions, different states of a competition or different places in photofinish photos) hence only one description. Unrelated images should be sent separately.

When the DocumentSubtype is PHOTOFINISH then no extensions are to be used to have all disciplines use the same structure.

2.2.4.2 Header Values

The following table describes the message header attributes.

Attribute	Value	Comment
CompetitionCode	CC @Competition	Unique ID for competition
DocumentCode	@ RSC	Depending on the message, the RSC could be: DD0000000 (sent at discipline level) DDG000000 (sent at gender level) DDGEEE000 (sent at event level) DDGEEEP00 (sent at phase level) DDGEEEPUU (sent at event unit level)
DocumentSubcode	S(10)	Picture number
DocumentType	DT_IMAGE	Image message
DocumentSubtype	PHOTOFINISH	Send PHOTOFINISH
Version	1..V	Version number associated to the message's content. Ascendant number
ResultStatus	SC @ResultStatus	Only applicable status is OFFICIAL
FeedFlag	"P"-Production "T"-Test	Test message or production message.
Date	Date	Date when the message is generated, expressed in the local time zone where the message was produced.
Time	Time	Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.
LogicalDate	Date	Logical Date of events. This is the same as the physical day except when the unit or message transmission extends after midnight. If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the message will all be dated Aug 2). The end of the logical day is defined by default at 03:00 a.m. For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the day of the correction. Logical Date is expressed in the local time zone where the message was produced.
Source	SC @Source	Code indicating the system which generated the message.
Serial	Numeric	Sequence number (positive integer) for ODF messages. Serial starts with 1 each day for each Source.

2.2.4.3 Trigger and Frequency

Trigger and frequency defined in ORIS (or PRIS).

Trigger also after any change.

2.2.4.4 Message Structure

The following table defines the structure of the message.

Level 1	Level 2	Level 3	Level 4
Competition (1,1)
	Code
	Image (1,N)
		Pos
		Version
		Revision
		ImageType
		ImageData (1,1)
			-

2.2.4.5 Message Values

Element: Competition (1,1)

Attribute

M/O

Value

Description

Code

CC @Competition

Unique ID for competition

Code is deprecated and value is duplicated in the header.

Element: Competition /Image (1,N)

Attribute	M/O	Value	Description
Pos	M	Numeric #0	Used as differentiator if there are multiple images in the message. In the case of different holes in golf the numbers 1..18 could be used.
Version	M	Numeric #0	Document Version
Revision	M	Numeric #0	Document Revision
ImageType	M	S(3)	Image type extension, jpg or png

Element: Competition /Image /ImageData (1,1)

Attribute	M/O	Value	Description
-	M	Free Text	The ImageData element has a body consisting of one Base64-encoded report (a jpeg or png file)

2.2.4.6 Message Sort

Sort by Competition /Image /Pos

2.2.5 Configuration

2.2.5.1 Description

The Configuration is a message containing general configuration.

Ideally the configuration should be provided before competition. However it may be possible that the configuration for one particular event, phase or event unit is not known in advance. In that case send the unknown attributes blank (Value='').

2.2.5.2 Header Values

The following table describes the message header attributes.

Attribute	Value	Comment
CompetitionCode	CC @Competition	Unique ID for competition
DocumentCode	DDGEEEPUU	DD according to CC @Discipline G according to CC @DisciplineGender EEE according to CC @Event P according to CC @Phase UU according to CC @Unit Sent this message for each Unit.
DocumentType	DT_CONFIG	Configuration message
Version	1..V	Version number associated to the message's content. Ascendant number
FeedFlag	"P"-Production "T"-Test	Test message or production message.
Date	Date	Date when the message is generated, expressed in the local time zone where the message was produced.
Time	Time	Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.
LogicalDate	Date	Logical Date of events. This is the same as the physical day except when the unit or message transmission extends after midnight. If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the message will all be dated Aug 2). The end of the logical day is defined by default at 03:00 a.m. For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the day of the correction. Logical Date is expressed in the local time zone where the message was produced.
Source	SC @Source	Code indicating the system which generated the message.
Serial	Numeric	Sequence number (positive integer) for ODF messages. Serial starts with 1 each day for each Source.

2.2.5.3 Trigger and Frequency

The message is sent prior to any ODF Sports message.

Trigger also after any major change, but considering that, if possible, the configuration for one particular event unit must be provided before the start list.

2.2.5.4 Message Structure

The following table defines the structure of the message.

Level 1	Level 2	Level 3	Level 4	Level 5	Level 6
Competition (1,1)
	Code
	Configs (1,1)
		Config (1,N)
			Gender
			Event
			Phase
			Unit
			ExtendedConfig (1,N)
				Type
				Code
				Pos
				Value
				ExtendedConfigItem (0,N)
					Code
					Pos
					Value

2.2.5.5 Message Values

Element: Competition (1,1)

Attribute	M/O	Value	Description
Code	M	CC @Competition	Unique ID for competition

Element: Configs /Config (1,N)

Attribute	M/O	Value	Description
Gender	M	CC @DisciplineGender	Gender code of the RSC. Include if information is by Gender, by Event, by Phase or by Event Unit. Otherwise, do not include.
Event	M	CC @Event	Event code of the RSC. Include if information is by Event, by Phase or by Event Unit. Otherwise, do not include.
Phase	M	CC @Phase	Phase code of the RSC. Include if information is by Phase or by Event Unit. Otherwise, do not include.
Unit	M	CC @Unit	Unit code of the RSC. Include if information is by Event Unit. Otherwise, do not include.

Element: Configs /Config /ExtendedConfig (1,N)

	Type	Code	Pos	Description
EC		DISTANCE	N/A	Element Expected: Always
	Attribute	M/O	Value	Description
	Value	O	Numeric	Send the total distance for the race in km.
	Sub Element: Configs /Config /ExtendedConfig /ExtendedConfigItem Expected: Always when applicable
	Attribute	Value	Description
	Code	FINISH_LOOP
	Pos	N/A	N/A
	Value	Numeric 0	Total number of the Finish Loops in the race Send if any Finish Loops exist
	Sub Element: Configs /Config /ExtendedConfig /ExtendedConfigItem Expected: Always
	Attribute	Value	Description
	Code	LAPS
	Pos	N/A	N/A
	Value	Numeric #0	Total Lap's numbers in the race
	Sub Element: Configs /Config /ExtendedConfig /ExtendedConfigItem Expected: Always when applicable
	Attribute	Value	Description
	Code	START_LOOP
	Pos	N/A	N/A
	Value	Numeric 0	Total number of the Start Loops in the race Send if any Start Loops exist
EC		FED_RANKING_DATE	N/A	Element Expected: As soon as the venue results has this information
	Attribute	M/O	Value	Description
	Value	M	YYYY-MM-DD	Send the date for UCI Ranking
EC		INTERMEDIATE	Numeric 0	Pos Description: Each intermediate point in the race where results are taken (Example: after start loop, after each lap/half lap, after the finish loop, at the end of the race, ..), from 1 to n. Where 1 is the first intermediate point and n is the finish the race. Element Expected: When available
	Attribute	M/O	Value	Description
	Value	O	Numeric ##0.0	Send distance in km at this intermediate point.
	Sub Element: Configs /Config /ExtendedConfig /ExtendedConfigItem Expected: When available
	Attribute	Value	Description
	Code	IS_LAST
	Pos	N/A	N/A
	Value	S(1)	Send 'Y'. Only send for the last Intermediate point (finish line).
	Sub Element: Configs /Config /ExtendedConfig /ExtendedConfigItem Expected: When available
	Attribute	Value	Description
	Code	TYPE
	Pos	N/A	N/A
	Value	SC @IntPtType	Send an indication of whether the timing point is the Start Loop (SL), a Half Lap (HL), a Lap (LAP), or the Finish Loop (FL) (see codes)
	Sub Element: Configs /Config /ExtendedConfig /ExtendedConfigItem Expected: If it applies
	Attribute	Value	Description
	Code	TYPE_DISTANCE
	Pos	N/A	N/A
	Value	Numeric #0.0	Send an indication of whether the timing point is a half or full lap. Where the TYPE is SL (Start Loop) or FL (Finish Loop) then do not send the TYPE_DISTANCE attribute, for the 'Half Lap' the value is "x.5" where x is the number of completed laps, and for the 'Lap' the value is "x.0" where x is the number of completed laps.
EC		INTERMEDIATES_TOTAL	N/A	Element Expected: When available
	Attribute	M/O	Value	Description
	Value	M	Numeric #0	Send the total number of intermediate points not including the start or finish.
EC		SECTION	Numeric 0	Pos Description: The number that identifies the section. A section is between two intermediate points, from 1 and n. Example: Section 1 is the section between start the race and intermediate point 1, in general the Section n is the section between Point n-1 and n)., from 2 to the total number of sections. Element Expected: When available.
	Attribute	M/O	Value	Description
	Value	O	Numeric ##0.00	Send distance in km.
	Sub Element: Configs /Config /ExtendedConfig /ExtendedConfigItem Expected: When available.
	Attribute	Value	Description
	Code	BEGIN
	Pos	N/A	N/A
	Value	Numeric 0	Send the intermediate point for the start of the section.
	Sub Element: Configs /Config /ExtendedConfig /ExtendedConfigItem Expected: When available.
	Attribute	Value	Description
	Code	END
	Pos	N/A	N/A
	Value	Numeric 0 Or S(1)	Send the intermediate point which is the end of the section (usually same a SECTION @Pos. For last section, send 'F'.

Sample (Sample)

....

</ExtendedConfig>

</ExtendedConfig>

</ExtendedConfig>

....

</ExtendedConfig>

</ExtendedConfig>

....

</ExtendedConfig>

</Config>

</Configs>

....

2.2.5.6 Message Sort

There is no message sorting rule.

2.2.6 Event Unit Weather conditions

2.2.6.1 Description

The 'Event Unit Weather Conditions' is a message containing the weather conditions in the Event Unit.

2.2.6.2 Header Values

The following table describes the message header attributes.

Attribute	Value	Comment
CompetitionCode	CC @Competition	Unique ID for competition
DocumentCode	DDGEEEPUU	DD according to CC @Discipline G according to CC @DisciplineGender EEE according to CC @Event P according to CC @Phase UU according to CC @Unit
DocumentType	DT_WEATHER	Weather conditions in the match message
Version	1..V	Version number associated to the message's content. Ascendant number
FeedFlag	"P"-Production "T"-Test	Test message or production message.
Date	Date	Date when the message is generated, expressed in the local time zone where the message was produced.
Time	Time	Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.
LogicalDate	Date	Logical Date of events. This is the same as the physical day except when the unit or message transmission extends after midnight. If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the message will all be dated Aug 2). The end of the logical day is defined by default at 03:00 a.m. For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the day of the correction. Logical Date is expressed in the local time zone where the message was produced.
Source	SC @Source	Code indicating the system which generated the message.
Serial	Numeric	Sequence number (positive integer) for ODF messages. Serial starts with 1 each day for each Source.

2.2.6.3 Trigger and Frequency

The message is sent if weather data conditions change during an event unit.

2.2.6.4 Message Structure

The following table defines the structure of the message.

Level 1	Level 2	Level 3	Level 4	Level 5
Competition (1,1)
	Code
	Weather (1,1)
		Conditions (1,N)
			Code
			Humidity
			Condition (0,3)
				Code
				Value
			Temperature (0,N)
				Code
				Unit
				Value

2.2.6.5 Message Values

Element: Competition (1,1)

Attribute	M/O	Value	Description
Code	M	CC @Competition	Unique ID for competition

Element: Weather /Conditions (1,N)

Attribute

M/O

Value

Description

Code

GL for generically, because this information will only be measured once.

Humidity

Numeric

##0

Humidity in %

Element: Weather /Conditions /Condition (0,3)

Send three times in the case of Winter conditions.

Attribute	M/O	Value	Description
Code	M	SKY	Weather conditions type
Value	M	CC @WeatherConditions	Codes that describe the Weather Condition.

Element: Weather /Conditions /Temperature (0,N)

Send with three different @Code in the case of Winter conditions.

Attribute	M/O	Value	Description
Code	M	AIR	Air
Unit	M	SC @TemperatureUnit	Metric system unit for temperature
Value	M	Numeric #0	Temperature in centigrade degrees (in case of positive temperature, do not send '+')

2.2.6.6 Message Sort

There is no special sort order requirement for this message. Usually, Conditions@code is the attribute used to sort the conditions.